home *** CD-ROM | disk | FTP | other *** search
- In article <2ksvn1$d7b@goofy.unisa.ac.za> koningj@risc1.unisa.ac.za (Gert Koning) writes:
- >From: koningj@risc1.unisa.ac.za (Gert Koning)
- >Subject: Text viewer for HGopher
- >Date: 28 Feb 1994 14:39:29 GMT
-
- >Can somebody point me to a good text viewer to be used with HGopher, since
- >Notepad can not display large files?
-
- Gert
-
- Try PFE (stands for Programmers File Editor) a Windows text file editor.Alan
- Phillips of Lancaster University wrote it. His address is
- A.Phillips@lancaster.ac.uk He should be able to tell you where to get it.
-
- >Many thanks,
- That's OK
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Steve Boyd email:boyd@ssmd.mrl.dsto.gov.au
- voice: +61 3 246 8305 Fax: +61 3 246 8999 __ |\
- / |_| \
- D E P A R T M E N T O F D E F E N C E .' \
- --------------------*-------------------- / \
- DEFENCE SCIENCE & TECHNOLOGY ORGINISATION \ __ /
- Melbourne \_.-' \_*/
- Ship Structures & Materials Division v
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- All opinions expressed her are mine, not necessarily DSTO's
- From news@bigblue.oit.unc.edu Fri Mar 4 04:20:40 1994
- Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
- id AA18030; Fri, 4 Mar 1994 00:58:00 -0500
- Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
- id AA09461; Fri, 4 Mar 1994 00:39:39 -0500
- Received: from GATEWAY by bigblue with netnews
- for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
- To: winsock@sunsite.unc.edu
- Date: Fri, 4 Mar 1994 04:20:40 GMT
- From: sdenney@runner.oit.unc.edu (Stephen Mark Denney)
- Message-Id: <1994Mar4.042040.14012@ringer.cs.utsa.edu>
- Organization: The Unversity of Texas at San Antonio
- Sender: ses
- Subject: ChameleonNFS 4.0 - Windows Printing Problem
-
- Hi,
- We just installed an upgrade to ChamNFS 4.0 (from 3.11) on
- a couple of PC's at work. I am noticing an interesting
- problem, namely with Novell printer connections. After
- doing the upgrade, I find that my NetWare network printer
- connections (assigned through Windows Print Manager) seem
- to "vanish" upon logout! After manually selecting any
- NetWare print queue, it will remain for the duration of the
- login - even if you close Windows and restart it. Only at
- Novell logout time is the connection "lost". This is happening
- on two different PC's, one of which was upgraded from Cham3.11,
- and one of which was a fresh install. Is anyone else having this
- problem? Otherwise, 4.0 is working great.
- I should mention that yes, we are checking the "permanent" box
- on the NetWare printer connections, but it isn't working like
- it did with 3.11. NetManage's tech support seems to be stumped;
- I've walked through the problem with them. Any ideas?
-
- Thanks, Steve
-
- p.s. this is my very first posting; i hope it works... :=}
- From news@bigblue.oit.unc.edu Fri Mar 4 13:55:52 1994
- Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
- id AA22717; Fri, 4 Mar 1994 01:28:01 -0500
- Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
- id AA31340; Fri, 4 Mar 1994 00:58:56 -0500
- Received: from GATEWAY by bigblue with netnews
- for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
- To: winsock@sunsite.unc.edu
- Date: Fri, 4 Mar 1994 13:55:52 GMT
- From: rogerm@tab.eunet.be
- Message-Id: <CM4Lwq.9sB@Belgium.EU.net>
- Organization: EUnet Belgium
- Sender: ses
- References: <news.5.00239866@asleeis.extern.ucsd>
- Subject: Re: WinTalk and Winsock---Incompatable?
-
-
-
- > the windock DLL...causing it to shut down (General Protection Fault thing
- > AGAIN ) I had to erase the installed wintalk and put it back in from the
- > zip file to get it running again... otherwise it crashed winsock when
- > wintalk was started...
- >
- > Now...I was wondering if there is a newer version out that fixes this or
- > what...I have v1.0 and could not find any other version... It is a nice
- > program if I could get it to work...
- >
- > I tried it under Windows...and OS/2....same thing...
-
- Look out for the ctl3d.dll, many programs use them. I had the same problem
- and ir turned out that the abovementioned dll got somehow replaced by an
- older version. So check the version, it should be 4.0 I think (I would
- have to look it up)
-
- Regards
-
- Roger
-
-